Technical reports

This specification defines interfaces to codecs for encoding and decoding of audio and video.

This specification does not specify or require any particular codec or method of encoding or decoding. The purpose of this specification is to provide JavaScript interfaces to implementations of existing codec technology developed elsewhere. Implementers may support any combination of codecs or none at all.

Editors

Chris Cunningham, Paul Adenot, Bernard Aboba.

Family:

WebCodecs

This registration is entered into the [webcodecs-codec-registry]. It describes, for AVC (H.264), the (1) fully qualified codec strings, (2) the VideoDecoderConfig.description bytes, and (3) the codec-specific extensions to the VideoEncoderConfig.

The registration is not intended to include any information on whether a codec format is encumbered by intellectual property claims. Implementers and authors are advised to seek appropriate legal counsel in this matter if they intend to implement or use a specific codec format. Implementers of WebCodecs are not required to support the AVC / H.264 codec.

Editors

Chris Cunningham, Paul Adenot, Bernard Aboba.

Family:

WebCodecs

This specification is a registry of supplementary members for the Web Application Manifest and the Web App Manifest - Application Information specifications that provide additional metadata to an application manifest to describe MiniApps. This JSON-based manifest file enables developers to set up basic information, window style, page route, and other information of a MiniApp. The manifest also includes information about the window style like the navigation bar, title, window background color, page routing information, and the widgets that are part of a MiniApp.

Editors

Martin Alvarez-Espinar, Yongjing ZHANG.

Family:

Miniapp

This document defines a policy language used to declare a set of content restrictions for a web resource, and a mechanism for transmitting the policy from a server to a client where the policy is enforced.

Editors

Mike West, Adam Barth, Daniel Veditz.

Family:

CSP

This document defines a mechanism by which web developers can control the resources which a particular page can fetch or execute, as well as a number of security-relevant policy decisions.

Editors

Mike West.

Family:

CSP

This document defines a mechanism by which a web page can embed a nested browsing context if and only if it agrees to enforce a particular set of restrictions upon itself.

Family:

CSP

This document serves as an official registry for all known global parameters, properties, and values used by the Decentralized Identifier ecosystem.

Editors

Orie Steele, Manu Sporny.

Family:

DID

This document sets out use cases and requirements for a new type of identifier.

Editors

Joe Andrieu, Phil Archer, Kim Duffy, Ryan Grant, Adrian Gropper.

Family:

DID

This document specifies the DID syntax, a common data model, core properties, serialized representations, DID operations, and an explanation of the process of resolving DIDs to the resources that they represent.

Editors

Drummond Reed, Manu Sporny, Markus Sabadello, Dave Longley, Christopher Allen.

Family:

DID

This document introduces a series of scenarios and a list of requirements guiding the work of the W3C Audio Working Group in its development of a web API for processing and synthesis of audio on the web.

Editors

Joe Berkovitz, Olivier Thereaux.

Family:

Web Audio API

This specification describes a high-level JavaScript API for processing and synthesizing audio in web applications. The primary paradigm is of an audio routing graph, where a number of AudioNode objects are connected together to define the overall audio rendering. The actual processing will primarily take place in the underlying implementation (typically optimized Assembly / C / C++ code), but direct JavaScript processing and synthesis is also supported.

Editors

Paul Adenot, Hongchan Choi.

Family:

Web Audio API

This specification intends to provide APIs to allow websites to create a floating video window always on top of other windows so that users may continue consuming media while they interact with other content sites, or applications on their device.

Editors

Francois Beaufort, Mounir Lamouri.

Family:

Picture-in-Picture

This document defines a set of ECMAScript APIs in WebIDL to allow data to be sent and received between a browser and server, utilizing [WEB-TRANSPORT-HTTP3]. This specification is being developed in conjunction with a protocol specification developed by the IETF WEBTRANS Working Group.

Editors

Bernard Aboba, Victor Vasiliev, Yutaka Hirano.

Family:

WebTransport

This specification enables web developers to show customized media metadata on platform UI, customize available platform media controls, and access platform media keys such as hardware keys found on keyboards, headsets, remote controls, and software keys found in notification areas and on lock screens of mobile devices.

Editors

Mounir Lamouri, Becca Hughes.

Family:

Media Session Standard

DCAT is an RDF vocabulary designed to facilitate interoperability between data catalogs published on the Web. This document defines the schema and provides examples for its use.

Editors

Riccardo Albertoni, David Browning, Simon Cox, Alejandra Gonzalez Beltran, Andrea Perego, Peter Winstanley.

Family:

DCAT

DCAT is an RDF vocabulary designed to facilitate interoperability between data catalogs published on the Web. This document defines the schema and provides examples for its use.

Editors

Riccardo Albertoni, David Browning, Simon Cox, Alejandra Gonzalez Beltran, Andrea Perego, Peter Winstanley.

Family:

DCAT

Recommends approaches for developers of rich internet applications to make widgets, navigation, and behaviors accessible using WAI-ARIA 1.1 roles, states, and properties.

Editors

Matthew King, JaEun Jemma Ku, James Nurthen, Zoë Bijl, Michael Cooper, Joseph Scheuhammer, Lisa Pappas, Richard Schwerdtfeger.

Family:

WAI-ARIA

Describes how user agents determine names and descriptions of accessible objects from web content languages and expose them in accessibility APIs.

Editors

Joanmarie Diggs, Bryan Garaventa, Michael Cooper.

Family:

WAI-ARIA

Defines how user agents map the WAI-ARIA Graphics Module markup to platform accessibility APIs.

Editors

Amelia Bellamy-Royds, Joanmarie Diggs, Michael Cooper.

Family:

WAI-ARIA

Defines a WAI-ARIA module of core roles, states and properties specific to web graphics. These semantics allow an author to express the logical structure of the graphic to assistive technologies, allowing assistive technologies to provide semantic navigation and adapt styling and interactive features.

Editors

Amelia Bellamy-Royds, Joanmarie Diggs, Michael Cooper.

Family:

WAI-ARIA

Accessibility of web content requires semantic information about widgets, structures and behaviors in order to allow assistive technologies to convey appropriate information to persons with disabilities. This specification defines a module encompassing an ontology of roles, states and properties specific to the digital publishing industry. These semantics are designed to allow an author to convey user interface behaviors and structural information to assistive technologies and to enable semantic navigation, styling and interactive features used by readers.

Editors

Matt Garrish, Tzviya Siegman, Markus Gylling, Shane McCarron.

Family:

WAI-ARIA

Describes how user agents should expose semantics of web content languages to various accessibility APIs in an interoperable manner. This helps users with disabilities to obtain and interact with information using assistive technologies. This specification defines core functionality; other specifications depend on and extend this for specific technologies.

Editors

Joanmarie Diggs, Joseph Scheuhammer, Richard Schwerdtfeger, Michael Cooper, Andi Snow-Weaver, Aaron Leventhal.

Family:

WAI-ARIA

Defines how user agents map the Digital Publishing WAI-ARIA Module markup to platform accessibility application programming interfaces (APIs). It is intended for user agent developers responsible for accessibility in their user agent so that they can support the accessibility content produced for digital publishing.

Editors

Richard Schwerdtfeger, Joanmarie Diggs.

Family:

WAI-ARIA

Recommends approaches for developers of rich internet applications to make widgets, navigation, and behaviors accessible using WAI-ARIA roles, states, and properties. WAI-ARIA 1.1 adds features new since WAI-ARIA 1.0 to complete the HTML + ARIA accessibility model. It is expected this will complement HTML 5.1.

Editors

Joanmarie Diggs, Shane McCarron, Michael Cooper, Richard Schwerdtfeger, James Craig.

Family:

WAI-ARIA

Describes how user agents should support keyboard navigation, respond to roles, states, and properties provided in Web content via WAI-ARIA, and expose this to accessibility APIs.

Editors

Joseph Scheuhammer, Michael Cooper.

Family:

WAI-ARIA

Accessibility of Web content to people with disabilities requires semantic information about widgets, structures, and behaviors, in order to allow Assistive Technologies to make appropriate transformations. This specification provides an ontology of roles, states, and properties that set out an abstract model for accessible interfaces and can be used to improve the accessibility and interoperability of Web Content and Applications. This information can be mapped to accessibility frameworks that use this information to provide alternative access solutions. Similarly, this information can be used to change the rendering of content dynamically using different style sheet properties. The result is an interoperable method for associating behaviors with document-level markup. This document is part of the WAI-ARIA suite described in the ARIA Overview.

Editors

James Craig, Michael Cooper.

Family:

WAI-ARIA

The Role Attribute defined in this specification allows the author to annotate markup languages with machine-extractable semantic information about the purpose of an element.

Editors

Shane McCarron.

Family:

WAI-ARIA

This specification defines the web developer rules (author conformance requirements) for the use of WAI ARIA attributes on HTML elements. It also defines requirements for Conformance Checking tools.

Editors

Steve Faulkner, Scott O'Hara, Patrick Lauke.

Family:

WAI-ARIA

Accessibility of web content requires semantic information about widgets, structures, and behaviors, in order to allow assistive technologies to convey appropriate information to persons with disabilities. This specification provides an ontology of roles, states, and properties that define accessible user interface elements and can be used to improve the accessibility and interoperability of web content and applications. These semantics are designed to allow an author to properly convey user interface behaviors and structural information to assistive technologies in document-level markup. This version adds features new since WAI-ARIA 1.1 [wai-aria-1.1] to improve interoperability with assistive technologies to form a more consistent accessibility model for [HTML] and [SVG2]. This specification complements both [HTML] and [SVG2].

This document is part of the WAI-ARIA suite described in the WAI-ARIA Overview.

Editors

Joanmarie Diggs, James Nurthen, Michael Cooper.

Family:

WAI-ARIA

Defines how user agents map HTML 5.1 elements and attributes to platform accessibility APIs. This promotes interoperable exposure of roles, states, properties, and events and helps to ensure that this information appears in a manner consistent with author intent.

Editors

Steve Faulkner, Alexander Surkov, Scott O'Hara, Bogdan Brinza, Jason Kiss, Cynthia Shelly.

Family:

WAI-ARIA

Recommends approaches for developers of rich internet applications to make widgets, navigation, and behaviors accessible using WAI-ARIA 1.1 roles, states, and properties. ARIA Practices 1.2 provides additional authoring guidance for new features in WAI-ARIA 1.2.

Editors

Matthew King, JaEun Jemma Ku, James Nurthen, Zoë Bijl, Michael Cooper, Joseph Scheuhammer, Lisa Pappas, Richard Schwerdtfeger.

Family:

WAI-ARIA

Describes how user agents should expose semantics of web content languages to various accessibility APIs in an interoperable manner. This helps users with disabilities to obtain and interact with information using assistive technologies. Core-AAM 1.2 provides additional mapping information for new features in WAI-ARIA 1.2.

Editors

Joanmarie Diggs, Michael Cooper, Richard Schwerdtfeger, Joseph Scheuhammer, Andi Snow-Weaver, Aaron Leventhal, Melanie Richards, James Craig, Alexander Surkov.

Family:

WAI-ARIA

This document describes how user agents determine the names and descriptions of accessible objects from web content languages. This information is in turn exposed through accessibility APIs so that assistive technologies can identify these objects and present their names or descriptions to users. Documenting the algorithm through which names and descriptions are to be determined promotes interoperable exposure of these properties among different accessibility APIs and helps to ensure that this information appears in a manner consistent with author intent.

Editors

Bryan Garaventa, Joanmarie Diggs, Michael Cooper.

Family:

WAI-ARIA

This document is a practical guide for developers on how to add accessibility information to HTML elements using ARIA, a markup mechanism for making Web content and Web applications more accessible to people with disabilities.

Editors

Steve Faulkner, David MacDonald.

Family:

WAI-ARIA

Describes how user agents map SVG markup to platform accessibility APIs. When user agents support this specification, SVG authors can create accessible rich internet applications, including charts, graphs, and other drawings.

Editors

Amelia Bellamy-Royds, Ian Pouncey.

Family:

WAI-ARIA

The Roadmap for Accessible Rich Internet Applications addresses the accessibility of dynamic Web content for people with disabilities. The roadmap introduces the technologies to map controls, Ajax live regions, and events to accessibility APIs, including custom controls used for Rich Internet Applications. The roadmap also describes new navigation techniques to mark common Web structures as menus, primary content, secondary content, banner information and other types of Web structures. These new technologies can be used to improve the accessibility and usability of Web resources by people with disabilities, without extensive modification to existing libraries of Web resources. This document is part of the WAI-ARIA suite described in the WAI-ARIA Overview.

Editors

Richard Schwerdtfeger.

Family:

WAI-ARIA

This document is a gap analysis and roadmap for the state of accessibility for people with learning and cognitive disabilities when using the Web and information technologies. It builds on the information presented in Cognitive Accessibility User Research and Cognitive Accessibility Issue Papers to evaluate where user needs remain to be met in technologies and accessibility guidelines. For various accessibility issues, this document provides a summary of issues and techniques, then identifies gaps and unmet user needs and suggest ways to meet these needs.

Editors

Lisa Seeman-Horwitz, Rachael Bradley Montgomery, Steve Lee, Ruoxi Ran.

Family:

TBD

The features in this specification extend or modify those found in Pointer Events, a W3C Recommendation that describes events and related interfaces for handling hardware agnostic pointer input from devices including a mouse, pen, touchscreen, etc. For compatibility with existing mouse based content, this specification also describes a mapping to fire Mouse Events for other pointer device types.

Editors

Matt Brubeck, Rick Byers, Patrick Lauke, Navid Zolghadr.

Family:

TBD

This specification defines an API enabling the creation and use of strong, attested, scoped, public key-based credentials by web applications, for the purpose of strongly authenticating users. Conceptually, one or more public key credentials, each scoped to a given WebAuthn Relying Party, are created by and bound to authenticators as requested by the web application. The user agent mediates access to authenticators and their public key credentials in order to preserve user privacy. Authenticators are responsible for ensuring that no operation is performed without user consent. Authenticators provide cryptographic proof of their properties to Relying Parties via attestation. This specification also describes the functional model for WebAuthn conformant authenticators, including their signature and attestation functionality.

Editors

Jeff Hodges, J.C. Jones, Michael Jones, Akshay Kumar, Emil Lundberg.

Family:

TBD

This registry is intended to enhance interoperability among implementations and users of [WEBCODECS]. In particular, this registry provides the means to identify and avoid collisions among codec strings and provides a mechanism to define codec-specific members of [WEBCODECS] codec configuration dictionaries.

This registry is not intended to include any information on whether a codec format is encumbered by intellectual property claims. Implementers and users are advised to seek appropriate legal counsel in this matter if they intend to implement or use a specific codec format. Implementers of WebCodecs are not required to support any particular codec nor registry entry.

Editors

Chris Cunningham, Paul Adenot, Bernard Aboba.

Family:

TBD

This CSS module describes how to collate style rules and assign values to all properties on all elements. By way of cascading and inheritance, values are propagated for all properties on all elements.

Editors

Elika Etemad, Miriam Suzanne, Tab Atkins Jr..

Family:

TBD

The features in this specification extend or modify those found in Pointer Events, a W3C Recommendation that describes events and related interfaces for handling hardware agnostic pointer input from devices including a mouse, pen, touchscreen, etc. For compatibility with existing mouse based content, this specification also describes a mapping to fire Mouse Events for other pointer device types.

Editors

Patrick Lauke, Navid Zolghadr, Matt Brubeck, Rick Byers.

Family:

TBD

This specification defines an API for specifying privacy and integrity policies on data, in the form of origin labels, and a mechanism for confining code according to such policies. This allows Web application authors and server operators to shared data with untrusted - buggy but not malicious - code (e.g., in a mashup scenario) yet impose restrictions on how the code can share the data further.

Editors

Deian Stefan.

Family:

TBD

This specification introduces and compares two client-side APIs for processing and synthesizing real-time audio streams in the browser.

Editors

Robert O'Callahan, Chris Rogers.

Family:

TBD

The Points of Interest Core describes a data model and XML syntax for representing information about points of interest on the World Wide Web.

Editors

Matt Womer.

Family:

TBD

Merchant validation is the process by which a payment handler validates the identity of a merchant against some value (usually some cryptographic challenge response). Validated merchants are allowed to interface with a payment handler. Details of how actual validation is performed is outside the scope of this specification.

Editors

Marcos Caceres.

Family:

Web Payments

EMVCo, FIDO Alliance and W3C have all taken steps to improve online payment security through the development of interoperable technical specifications. In this document we describe the core capabilities provided by some of their specifications, what problems can be solved by combining them, and potential changes to improve how they work together.

Editors

Ian Jacobs.

Family:

Web Payments

This document outlines the W3C Web Payments ecosystem by introducing readers to the goals of the ecosystem, messages, roles, and information flow in the system.

Editors

Manu Sporny, Adrian Hope-Bailie, Nick Telford-Reed, Roy McElmurry, Dapeng Liu.

Family:

Web Payments

The Payment Request API provides a standard way to initiate payment requests from Web pages and applications. User agents implementing that API prompt the user to select a way to handle the payment request, after which the user agent returns a payment response to the originating site. This specification defines capabilities that enable Web applications to handle payment requests.

Editors

Adrian Hope-Bailie, Jason Normore, Ian Jacobs, Rouslan Solomakhin, Jinho Bang, Tommy Thorsen, Adam Roach.

Family:

Web Payments

The Basic Card Payment specification describes the data formats used by the PaymentRequest API to support payment by payment cards such as credit or debit cards.

Editors

Marcos Caceres, Domenic Denicola, Zach Koch, Roy McElmurry, Adrian Bateman.

Family:

Web Payments

The Payment Request API requires that merchants supply a list of identifiers for supported payment methods. This document defines those identifier strings and how they are created.

Editors

Marcos Caceres, Domenic Denicola, Zach Koch, Roy McElmurry.

Family:

Web Payments

This specification defines the machine-readable manifest file, known as a payment method manifest, describing how a payment method participates in the Web Payments ecosystem, and how such files are to be used.

Editors

Dapeng Liu, Domenic Denicola, Zach Koch.

Family:

Web Payments

This specification provides an API for representing file objects in web applications, as well as programmatically selecting them and accessing their data.

Editors

Marijn Kruisselbrink, Arun Ranganathan.

Family:

File API

This document defines the concept of an "image resource" and a corresponding WebIDL ImageResource dictionary. Web APIs can use the ImageResource dictionary to represent an image resource in contexts where an HTMLImageElement is not suitable or available (e.g., in a Worker).

Editors

Aaron Gustafson, Rayan Kanso, Marcos Caceres.

Family:

Image Resource

This CSS module defines properties for text manipulation and specifies their processing model. It covers line breaking, justification and alignment, white space handling, and text transformation.

Editors

Elika Etemad, Koji Ishii, Florian Rivoal.

Family:

CSS Text

This module defines properties for text manipulation and specifies their processing model. It covers line breaking, justification and alignment, white space handling, and text transformation.

Editors

Elika Etemad, Koji Ishii, Alan Stearns, Florian Rivoal.

Family:

CSS Text

This specification defines a JavaScript interface that provides the current time in sub-millisecond resolution and such that it is not subject to system clock skew or adjustments.

Editors

Ilya Grigorik.

Family:

Performance instrumentation

This specification defines an interface to help web developers measure the performance of their applications by giving them access to high precision timestamps.

Editors

Ilya Grigorik.

Family:

Performance instrumentation

This specification defines an interface for web applications to access timing information related to navigation and elements. It is used by other specifications, like User Timing.

Editors

Jatinder Mann, Zhiheng Wang.

Family:

Performance instrumentation

This document provides an interface for web applications to access timing information related to navigation and elements.

Editors

Zhiheng Wang.

Family:

Performance instrumentation

This specification defines an interface for web applications to access the complete timing information for resources in a document.

Editors

Yoav Weiss, Noam Rosenthal, Ilya Grigorik, Todd Reifsteck, Arvind Jain, Jatinder Mann, Zhiheng Wang, Anderson Quach.

Family:

Performance instrumentation

This specification defines an API that provides the current time in sub-millisecond resolution and such that it is not subject to system clock skew or adjustments.

Editors

Yoav Weiss, Ilya Grigorik, James Simonsen, Jatinder Mann.

Family:

Performance instrumentation

This specification defines an interface to help web developers measure the performance of their applications by giving them access to high precision timestamps.

Editors

Nicolas Pena Moreno, Ilya Grigorik, Jatinder Mann, Zhiheng Wang, Anderson Quach.

Family:

Performance instrumentation

This document provides an interface for web applications to access timing information related to navigation and elements.

Editors

Yoav Weiss, Ilya Grigorik, Tobin Titus, Jatinder Mann, Arvind Jain.

Family:

Performance instrumentation

Server Timing, part of the performance timeline metrics, provides API access to request-response cycle performance metrics communicated from the server to the user agent.

Editors

Charles Vazac, Ilya Grigorik.

Family:

Performance instrumentation

This specification extends the High Resolution Time specification by providing methods to store and retrieve high resolution performance metric data.

Editors

Ilya Grigorik.

Family:

Performance instrumentation

This registry is intended to provide a central location for enumerating identified interface types of PerformanceEntry objects, which contain various data metrics for the the full lifecycle of a web application.

Editors

Philippe Le Hégaret.

Family:

Performance instrumentation

The reporting API provides a generic reporting framework which allows Web developers to associate a set of named reporting endpoints with an origin. Various platform features (like Content Security Policy, Network Error Reporting, and others) will use these endpoints to deliver feature-specific reports in a consistent manner.

Editors

Douglas Creager, Ilya Grigorik, Paul Meyer, Mike West.

Family:

Performance instrumentation

This document defines an API that can be used to capture a series of key moments (First Paint, First Contentful Paint) during pageload which developers care about.

Editors

Shubhie Panicker.

Family:

Performance instrumentation

This specification defines an interface for web applications to access timing information related to HTML elements.

Editors

Arvind Jain, Todd Reifsteck, Jatinder Mann, Zhiheng Wang, Anderson Quach.

Family:

Performance instrumentation

This document defines a set of APIs that allow local media, including audio and video, to be requested from a platform, media to be sent over the network to another browser or device implementing the appropriate set of real-time protocols, and media received from another browser or device to be processed and displayed locally.

Editors

Cullen Jennings, Bernard Aboba, Jan-Ivar Bruaroey, Henrik Boström, youenn fablet, Daniel Burnett, Adam Bergkvist, Anant Narayanan.

Family:

Media Capture

This document specifies methods and camera settings to produce photographic image capture. The source of images is, or can be referenced via a MediaStreamTrack.

Editors

Miguel Casas-sanchez, Rijubrata Bhaumik, Giridhar Mandyam.

Family:

Media Capture

The Open Screen Protocol is a suite of network protocols that allow user agents to implement the Presentation API and the Remote Playback API in an interoperable fashion.

Editors

Mark Foltz.

Family:

Media Capture

This document defines a recording API for use with MediaStreams.

Editors

Miguel Casas-sanchez, James Barnett, Travis Leithead.

Family:

Media Capture

This document defines how a user's display, or parts thereof, can be used as the source of a media stream using getOutputMedia, an extension to the Media Capture API [GETUSERMEDIA].

Editors

Martin Thomson, Keith Griffin, Suhas Nandakumar, Henrik Boström, Jan-Ivar Bruaroey.

Family:

Media Capture

This specification extends MediaStreamTrack to provide a media-content hint attribute. This optional hint permits MediaStreamTrack consumers such as PeerConnection or MediaRecorder to encode or process track media with methods more appropriate to the type of content that is being consumed.

Editors

Harald Alvestrand.

Family:

Media Capture

This document defines how a stream of media can be captured from a DOM element, such as a <video>, <audio>, or <canvas> element, in the form of a MediaStream.

Editors

Martin Thomson, Miguel Casas-sanchez, Emircan Uysaler.

Family:

Media Capture

This specification extends the Media Capture and Streams specification to allow a depth stream to be requested from 3D cameras.

Editors

Anssi Kostiainen, Ningxin Hu, Aleksandar Stojiljkovic, Rob Manson.

Family:

Media Capture

This document collates the scenarios that are target use cases for the Media Capture API that enables access to media input capabilities for Web applications using Javascript.

Editors

Travis Leithead.

Family:

Media Capture

Defines a low-level interface that represents gamepad devices.

Editors

Steve Agoston, James Hollyer, Matthew Reynolds, Brandon Jones, Scott Graham, Theodore Mielczarek.

Family:

Gamepad

This specification defines an API enabling the creation and use of strong, attested, scoped, public key-based credentials by web applications, for the purpose of strongly authenticating users. Conceptually, one or more public key credentials, each scoped to a given WebAuthn Relying Party, are created by and bound to authenticators as requested by the web application. The user agent mediates access to authenticators and their public key credentials in order to preserve user privacy. Authenticators are responsible for ensuring that no operation is performed without user consent. Authenticators provide cryptographic proof of their properties to Relying Parties via attestation. This specification also describes the functional model for WebAuthn conformant authenticators, including their signature and attestation functionality.

Editors

Jeff Hodges, J.C. Jones, Michael Jones, Akshay Kumar, Emil Lundberg.

Family:

Web Authentication

This specification defines an API that enables web pages to access WebAuthn compliant strong cryptographic credentials through browser script.

Editors

Dirk Balfanz, Alexei Czeskis, Jeff Hodges, J.C. Jones, Michael Jones, Akshay Kumar, Huakai Liao, Rolf Lindemann, Emil Lundberg.

Family:

Web Authentication

This specification defines a manifest, which provides developers with a centralized place to put metadata about a web application.

Editors

Marcos Caceres, Kenneth Christiansen, Mounir Lamouri, Anssi Kostiainen, Matt Giuca, Aaron Gustafson.

Family:

Manifest

EPUB Accessibility Techniques defines discovery and content accessibility requirements for EPUB Publications.

Editors

Matt Garrish, George Kerscher, Charles LaPierre, Gregorio Pellegrino, Avneesh Singh.

Family:

EPUB

This document provides a starting point for content authors and software developers wishing to understand the EPUB® 3 specifications. It consists entirely of informative overview material that describes the features available in EPUB 3.

The current version of EPUB 3 is defined in [EPUB-33], which represents the second minor revision of the standard. The substantive changes since EPUB 3.2 [EPUB-32] are documented in a separate section in the EPUB 3.3 document itself.

Editors

Garth Conboy, Matt Garrish, Daniel Weck.

Family:

EPUB

This specification, EPUB Multiple-Rendition Publications, defines the creation and rendering of EPUB® Publications consisting of more than one Rendition.

Editors

Matt Garrish.

Family:

EPUB

EPUB® 3 defines a ../distribution and interchange format for digital publications and documents. The EPUB format provides a means of representing, packaging, and encoding structured and semantically enhanced Web content — including HTML, CSS, SVG and other resources — for distribution in a single-file container.

This specification defines the conformance requirements for EPUB® 3 Reading Systems — the user agents that render EPUB Publications.

Editors

Dave Cramer, Matt Garrish, Ivan Herman, Garth Conboy, Marisa DeMeglio, Daniel Weck.

Family:

EPUB

EPUB® 3 defines a ../distribution and interchange format for digital publications and documents. The EPUB format provides a means of representing, packaging, and encoding structured and semantically enhanced Web content — including HTML, CSS, SVG, and other resources — for distribution in a single-file container.

This specification defines the authoring requirements for EPUB Publications and represents the third major revision of the standard.

Editors

Matt Garrish, Ivan Herman, Dave Cramer, Garth Conboy, Marisa DeMeglio, Daniel Weck.

Family:

EPUB

This document specifies content conformance requirements for verifying the accessibility of EPUB Publications. It also specifies accessibility metadata requirements for the discoverability of EPUB Publications.

Editors

Matt Garrish, George Kerscher, Charles LaPierre, Gregorio Pellegrino, Avneesh Singh.

Family:

EPUB

This CSS module describes a way for authors to define a transformation to be applied to the time of an animation. This can be used to produce animations that mimic physical phenomena such as momentum or to cause the animation to move in discrete steps producing robot-like movement.

Editors

Brian Birtles, Dean Jackson, Matt Rakow, Shane Stephens.

Family:

CSS Easing Functions

This document describes and prioritises gaps for the support of the Tamil script on the Web and in eBooks. In particular, it is concerned with text layout. It checks that needed features are supported in W3C specifications, in particular HTML and CSS and those relating to digital publications. It also checks whether the features have been implemented in browsers and ereaders.

Editors

Richard Ishida.

Family:

Language Gap Analysis

This document describes and prioritises gaps for the support of languages using the Bengali script on the Web and in eBooks. In particular, it is concerned with text layout. It checks that needed features are supported in W3C specifications, in particular HTML and CSS and those relating to digital publications. It also checks whether the features have been implemented in browsers and ereaders.

Editors

Richard Ishida.

Family:

Language Gap Analysis

This document describes and prioritises gaps for the support of the Devanagari script on the Web and in eBooks. In particular, it is concerned with text layout. It checks that needed features are supported in W3C specifications, in particular HTML and CSS and those relating to digital publications. It also checks whether the features have been implemented in browsers and ereaders.

Editors

Akshat Joshi, Richard Ishida.

Family:

Language Gap Analysis

This document describes and prioritises gaps for the support of languages using the Thai script on the Web and in eBooks. In particular, it is concerned with text layout. It checks that needed features are supported in W3C specifications, in particular HTML and CSS and those relating to digital publications. It also checks whether the features have been implemented in browsers and ereaders.

Editors

Richard Ishida.

Family:

Language Gap Analysis

This document describes and prioritises gaps for the support of languages using the Gujarati script on the Web and in eBooks. In particular, it is concerned with text layout. It checks that needed features are supported in W3C specifications, in particular HTML and CSS and those relating to digital publications. It also checks whether the features have been implemented in browsers and ereaders.

Editors

Neha Gupta, Richard Ishida.

Family:

Language Gap Analysis

This document describes and prioritises gaps for the support of Adlam on the Web and in eBooks. In particular, it is concerned with text layout. It checks that needed features are supported in W3C specifications, in particular HTML and CSS and those relating to digital publications. It also checks whether the features have been implemented in browsers and ereaders. This is a preliminary analysis.

Editors

Richard Ishida.

Family:

Language Gap Analysis

This document describes and prioritises gaps for the support of Arabic and Persian languages on the Web and in eBooks. In particular, it is concerned with text layout. It checks that needed features are supported in W3C specifications, in particular HTML and CSS and those relating to digital publications. It also checks whether the features have been implemented in browsers and ereaders.

Editors

Shervin Afshar, Richard Ishida.

Family:

Language Gap Analysis

This document describes and prioritises gaps for the support of N’Ko on the Web and in eBooks. In particular, it is concerned with text layout. It checks that needed features are supported in W3C specifications, in particular HTML and CSS and those relating to digital publications. It also checks whether the features have been implemented in browsers and ereaders. This is a preliminary analysis.

Editors

Richard Ishida.

Family:

Language Gap Analysis

This document describes and prioritises gaps for the support of Hebrew on the Web and in eBooks. In particular, it is concerned with text layout. It checks that needed features are supported in W3C specifications, in particular HTML and CSS and those relating to digital publications. It also checks whether the features have been implemented in browsers and ereaders. This is a preliminary analysis.

Editors

Richard Ishida.

Family:

Language Gap Analysis

This document describes and prioritises gaps for the support of German on the Web and in eBooks. In particular, it is concerned with text layout. It checks that needed features are supported in W3C specifications, in particular HTML and CSS and those relating to digital publications. It also checks whether the features have been implemented in browsers and ereaders. This is a preliminary analysis.

Editors

Richard Ishida.

Family:

Language Gap Analysis

This document describes and prioritises gaps for the support of French on the Web and in eBooks. In particular, it is concerned with text layout. It checks that needed features are supported in W3C specifications, in particular HTML and CSS and those relating to digital publications. It also checks whether the features have been implemented in browsers and ereaders. This is a preliminary analysis.

Editors

Richard Ishida.

Family:

Language Gap Analysis

This document describes and prioritises gaps for the support of Osage using the Osage script on the Web and in eBooks. In particular, it is concerned with text layout. It checks that needed features are supported in W3C specifications, in particular HTML and CSS and those relating to digital publications. It also checks whether the features have been implemented in browsers and ereaders. This is a preliminary analysis.

Editors

Richard Ishida.

Family:

Language Gap Analysis

This document describes and prioritises gaps for the support of Japanese on the Web and in eBooks. In particular, it is concerned with text layout. It checks that needed features are supported in W3C specifications, in particular HTML and CSS and those relating to digital publications. It also checks whether the features have been implemented in browsers and ereaders.

Editors

Richard Ishida.

Family:

Language Gap Analysis

This document describes and prioritises gaps for the support of the Traditional Mongolian script (Hudum) on the Web and in eBooks. In particular, it is concerned with text layout. It checks that needed features are supported in W3C specifications, in particular HTML and CSS and those relating to digital publications. It also checks whether the features have been implemented in browsers and ereaders.

Editors

Richard Ishida.

Family:

Language Gap Analysis

This document describes and prioritises gaps for the support of Lao on the Web and in eBooks. In particular, it is concerned with text layout. It checks that needed features are supported in W3C specifications, in particular HTML and CSS and those relating to digital publications. It also checks whether the features have been implemented in browsers and ereaders.

Editors

Richard Ishida.

Family:

Language Gap Analysis

This document describes and prioritises gaps for the support of Dutch on the Web and in eBooks. In particular, it is concerned with text layout. It checks that needed features are supported in W3C specifications, in particular HTML and CSS and those relating to digital publications. It also checks whether the features have been implemented in browsers and ereaders.

Editors

Bert Bos, Richard Ishida.

Family:

Language Gap Analysis

This document describes and prioritises gaps for the support of languages using the Ethiopic script on the Web and in eBooks. In particular, it is concerned with text layout. It checks that needed features are supported in W3C specifications, in particular HTML and CSS and those relating to digital publications. It also checks whether the features have been implemented in browsers and ereaders.

Editors

Richard Ishida.

Family:

Language Gap Analysis

This document describes and prioritises gaps for the support of Georgian on the Web and in eBooks. In particular, it is concerned with text layout. It checks that needed features are supported in W3C specifications, in particular HTML and CSS and those relating to digital publications. It also checks whether the features have been implemented in browsers and ereaders.

Editors

Richard Ishida.

Family:

Language Gap Analysis

This document describes and prioritises gaps for the support of Modern Greek on the Web and in eBooks. In particular, it is concerned with text layout. It checks that needed features are supported in W3C specifications, in particular HTML and CSS and those relating to digital publications. It also checks whether the features have been implemented in browsers and ereaders.

Editors

Richard Ishida.

Family:

Language Gap Analysis

This document describes and prioritises gaps for the support of Hungarian on the Web and in eBooks. In particular, it is concerned with text layout. It checks that needed features are supported in W3C specifications, in particular HTML and CSS and those relating to digital publications. It also checks whether the features have been implemented in browsers and ereaders.

Editors

Ivan Herman, Richard Ishida.

Family:

Language Gap Analysis

This document describes and prioritises gaps for the support of Inuktitut & Cree using Canadian Syllabics on the Web and in eBooks. In particular, it is concerned with text layout. It checks that needed features are supported in W3C specifications, in particular HTML and CSS and those relating to digital publications. It also checks whether the features have been implemented in browsers and ereaders.

Editors

Richard Ishida.

Family:

Language Gap Analysis

This document describes and prioritises gaps for the support of Cherokee on the Web and in eBooks. In particular, it is concerned with text layout. It checks that needed features are supported in W3C specifications, in particular HTML and CSS and those relating to digital publications. It also checks whether the features have been implemented in browsers and ereaders.

Editors

Richard Ishida.

Family:

Language Gap Analysis

This document describes and prioritises gaps for the support of Khmer on the Web and in eBooks. In particular, it is concerned with text layout. It checks that needed features are supported in W3C specifications, in particular HTML and CSS and those relating to digital publications. It also checks whether the features have been implemented in browsers and ereaders.

Editors

Richard Ishida.

Family:

Language Gap Analysis

This document describes and prioritises gaps for the support of Javanese written with the Javanese script on the Web and in eBooks. In particular, it is concerned with text layout. It checks that needed features are supported in W3C specifications, in particular HTML and CSS and those relating to digital publications. It also checks whether the features have been implemented in browsers and ereaders.

Editors

Richard Ishida.

Family:

Language Gap Analysis

This document describes and prioritises gaps for the support of Simplified and Traditional Chinese on the Web and in eBooks. In particular, it is concerned with text layout. It checks that needed features are supported in W3C specifications, in particular HTML and CSS and those relating to digital publications. It also checks whether the features have been implemented in browsers and ereaders.

Editors

Fuqiao Xue, Richard Ishida.

Family:

Language Gap Analysis

This document describes and prioritises gaps for the support of Tibetan on the Web and in eBooks. In particular, it is concerned with text layout. It checks that needed features are supported in W3C specifications, in particular HTML and CSS and those relating to digital publications. It also checks whether the features have been implemented in browsers and ereaders.

Editors

Richard Ishida.

Family:

Language Gap Analysis

This document describes and prioritises gaps for the support of languages using the Gurmukhi script on the Web and in eBooks. In particular, it is concerned with text layout. It checks that needed features are supported in W3C specifications, in particular HTML and CSS and those relating to digital publications. It also checks whether the features have been implemented in browsers and ereaders.

Editors

Akshat Joshi, Richard Ishida.

Family:

Language Gap Analysis

This document points browser implementers and specification developers to information about how to support typographic features of scripts or writing systems from around the world, and also points to relevant information in specifications, to tests, and to useful articles and papers. It is not exhaustive, and will be added to from time to time.

Editors

Richard Ishida.

Family:

Language Gap Analysis

This specification defines the syntax and semantics of XSLT 2.0, a language for transforming XML documents into other XML documents.

XSLT 2.0 is a revised version of the XSLT 1.0 Recommendation [XSLT 1.0] published on 16 November 1999.

XSLT 2.0 is designed to be used in conjunction with XPath 2.0, which is defined in [XPath 2.0]. XSLT shares the same data model as XPath 2.0, which is defined in [Data Model], and it uses the library of functions and operators defined in [Functions and Operators].

XSLT 2.0 also includes optional facilities to serialize the results of a transformation, by means of an interface to the serialization component described in [XSLT and XQuery Serialization].

This document contains hyperlinks to specific sections or definitions within other documents in this family of specifications. These links are indicated visually by a superscript identifying the target specification: for example XP for XPath, DM for the XDM data model, FO for Functions and Operators.

Editors

Michael Kay.

Family:

Xquery & XSLT

This document specifies goals and requirements for the XQuery Scripting Extension.

Editors

Daniel Engovatov, Daniela Florescu, Giorgio Ghelli.

Family:

Xquery & XSLT

This document specifies usage scenarios for the XQuery Scripting Extension.

Editors

John Snelson.

Family:

Xquery & XSLT

This specification defines the syntax and semantics of XSLT 3.0, a language for transforming XML documents into other XML documents.

Editors

Michael Kay.

Family:

Xquery & XSLT

XQueryX 3.1 defines an XML syntax for the semantics defined by XQuery 3.1.

Editors

Jim Melton, Josh Spiegel.

Family:

Xquery & XSLT

The XPath and XQuery Data Model (XDM) 3.1 defines the data model on which all operations of XPath 3.1, XQuery 3.1, and XSLT 3.1 operate.

Editors

Norman Walsh, John Snelson, Andrew Coleman.

Family:

Xquery & XSLT

XPath and XQuery Functions and Operators 3.0 defines a library of functions available for use in XPath, XQuery, XSLT and other languages.

Editors

Michael Kay.

Family:

Xquery & XSLT

This document defines serialization of an instance of the XQuery and XPath Data model Data Model into a sequence of octets, such as into XML, text, HTML, JSON.

Editors

Andrew Coleman, Michael Sperberg-McQueen.

Family:

Xquery & XSLT

XQuery 3.1 is a versatile query and application development language, capable of processing the information content of diverse data sources including structured and semi-structured documents, relational databases and tree-bases databases. The XQuery language is designed to support powerful optimizations and pre-compilation leading to very efficient searches over large amounts of data, including over so-called XML-native databases that read and write XML but have an efficient internal storage.

Editors

Jonathan Robie, Michael Dyck, Josh Spiegel.

Family:

Xquery & XSLT

XPath is an expression language that allows the processing of values conforming to the data model defined in the XQuery and Xpath Data Model.

Editors

Jonathan Robie, Michael Dyck, Josh Spiegel.

Family:

Xquery & XSLT

This document defines an update facility that extends the XML Query language, XQuery. The XQuery Update Facility 3.0 provides expressions that can be used to make persistent changes to instances of the XQuery and XPath Data Model 3.0.

Editors

John Snelson, Jim Melton.

Family:

Xquery & XSLT

This document specifies goals, requirements and use cases for the XQuery Update Facility 3.0.

Editors

Andrew Coleman.

Family:

Xquery & XSLT

This document specifies goals and requirements for XQuery 3.1.

Editors

Jonathan Robie.

Family:

Xquery & XSLT

This document specifies requirements and use cases for Full-Text Search for use in XQuery 3.0 and XPath 3.0.

Editors

Pat Case.

Family:

Xquery & XSLT

This document defines the syntax and formal semantics of XQuery and XPath Full Text 3.0, which is a language that extends XQuery 3.0 [XQuery 3.0: An XML Query Language] and XPath 3.0 [XML Path Language (XPath) 3.0] with full-text search capabilities.

Editors

Mary Holstege, Jim Melton.

Family:

Xquery & XSLT

This specification defines an extension to [XQuery 1.0] and [XQuery Update Facility]. Expressions can be evaluated in a specific order, with later expressions seeing the effects of the expressions that came before them. This specification introduces the concept of a block with local variable declarations, as well as several new kinds of expressions, including assignment, while, and exit expressions.

Editors

John Snelson, Don Chamberlin, Daniel Engovatov, Dana Florescu, Giorgio Ghelli, Jim Melton, Jerome Simeon.

Family:

Xquery & XSLT

XPath and XQuery Functions and Operators 3.0 (renamed from XPath and XQuery Functions and Operators 1.1 to align with the family of "3.0" specifications) defines a library of functions available for use in XPath 3.0, XQuery 3.0, and XSLT 3.0. Some of the new features since XPath 2.0 and XQuery 1.0 Functions and Operators include:

• More than 30 new functions have been added, including functions transferred from the XSLT 2.0 specification into Functions and Operators 3.0 and additional versions of existing functions with different signatures
• The syntax for regular expressions was enhanced to allow for non-capturing groups; additionally, a new flag value was added for regular-expression-related functions that accept a flag argument
• Support for function items has been added in the form of a number of new functions
• The description of fn:error was rewritten to accommodate the addition of try/catch capabilities in XQuery 3.0

Editors

Michael Kay.

Family:

Xquery & XSLT

XSLT and XQuery Serialization 3.0 (renamed from XQueryX 1.1 to align with the family of "3.0" specifications) defines serialization of an instance of XDM 3.0 into a sequence of octets. Important new features in Serialization 3.0 include:

• Supports serialization of function items
• Adds a definition of a suppress-indentation serialization parameter
• Clarifies how minimized attributes, as well as the "script" and "style" elements, are handled under the rules of the HTML output method

Editors

Henry Zongaro, Andrew Coleman, Michael Sperberg-McQueen.

Family:

Xquery & XSLT

The design of XQuery 3.0 was supported by use cases gathered following the XQuery 1.0 development timeframe. This Use Cases document (renamed from XQuery Use Cases 1.1 to align with the family of "3.0" specifications) corrects one Use Case.

Editors

Jonathan Robie, Tim Kraska.

Family:

Xquery & XSLT

XQuery 3.0 (renamed from XQuery 1.1 to align with the family of "3.0" specifications) is a versatile markup language, capable of labeling the information content of diverse data sources including structured and semi-structured documents, relational databases, and object repositories. Important new features since XQuery 1.0 include:

• The "group by" clause, windowing ("tumbling window" and "sliding window"), the "count" clause, and the "allowing empty" clause in FLWOR expressions
• A try/catch capability to support application handling of errors
• Literal function items, inline functions, dynamic function invocations, and function item coercion
• Nondeterministic functions and private functions
• A value-based switch expression (analogous to the existing typeswitch expression)
• Computed namespace constructors
• Declaration of serialization parameters
• Support for new Functions and Operators 3.0 capabilities
• Cleaner definition of module import

Editors

Jonathan Robie, Don Chamberlin, Michael Dyck, John Snelson.

Family:

Xquery & XSLT

XPath 3.0 (renamed from XPath 2.1 to align with the family of "3.0" specifications) is an expression language that allows the processing of values conforming to the data model defined in [XQuery and XPath Data Model (XDM) 3.0]. Some of the important new features since XPath 2.0 are:

• Literal function items, inline functions, dynamic function invocations, and function item coercion
• Clarification of rules associated with sequence type matching
• let expressions
• EQNames (QNames with a namespace URI instead of a namespace prefix)
• Support for union types in casting and function arguments

Editors

Jonathan Robie, Don Chamberlin, Michael Dyck, John Snelson.

Family:

Xquery & XSLT

XQueryX 3.0 (renamed from XQueryX 1.1 to align with the family of "3.0" specifications) defines an XML syntax for the semantics defined by XQuery 3.0. This publication is aligned with XQuery 3.0

Editors

Jim Melton.

Family:

Xquery & XSLT

The design of XQuery 3.0 was driven by requirements gathered following the XQuery 1.0 development timeframe. This Requirements document (renamed from XQuery Requirements 1.1 to align with the family of "3.0" specifications) provides an update on the status of each requirements.

Editors

Jonathan Robie, Daniel Engovatov.

Family:

Xquery & XSLT

XPath and XQuery Data Model (XDM) 3.0 (renamed from XPath and XQuery Functions and Operators (XDM) 1.1 to align with the family of "3.0" specifications) defines the data model on which all operations of XPath 3.0, XQuery 3.0, and XSLT 3.0 operate. In this version of XDM, two new data types have been added:

• From XML Schema 1.1 Part 2 (Datatypes), the xs:dateTimeStamp data type
• To support XPath 3.0's and XQuery 3.0's function item capabilities, a function item data type

Editors

Norman Walsh, Anders Berglund, John Snelson.

Family:

Xquery & XSLT

This document defines the syntax and formal semantics of XQuery and XPath Full Text 1.0 which is a language that extends XQuery 1.0 [XQuery 1.0: An XML Query Language] and XPath 2.0 [XML Path Language (XPath) 2.0] with full-text search capabilities.

Editors

Pat Case, Michael Dyck, Mary Holstege, Sihem Amer-Yahia, Chavdar Botev, Stephen Buxton, Jochen Dörre, Jim Melton, Michael Rys, Jayavel Shanmugasundaram.

Family:

Xquery & XSLT

This document defines an update facility that extends the XML Query language, XQuery. The XQuery Update Facility provides expressions that can be used to make persistent changes to instances of the XQuery 1.0 and XPath 2.0 Data Model.

Editors

Don Chamberlin, Jonathan Robie, Michael Dyck, Daniela Florescu, Jim Melton, Jerome Simeon.

Family:

Xquery & XSLT

This document specifies usage scenarios for the XQuery Update Facility.

Editors

Ioana Manolescu, Jonathan Robie.

Family:

Xquery & XSLT

This document specifies goals and requirements for the XQuery Update Facility.

Editors

Don Chamberlin, Jonathan Robie.

Family:

Xquery & XSLT

The document specifies requirements for Full-Text Search for use in XQuery [XQuery] and XPath [XPath].

Editors

Stephen Buxton, Pat Case, Michael Rys.

Family:

Xquery & XSLT

This document specifies usage scenarios for full-text queries as part of XML Query [XQuery 1.0: An XML Query Language] and XPath [XML Path Language (XPath) 2.0].

Editors

Pat Case, Sihem Amer-Yahia.

Family:

Xquery & XSLT

This document defines formally the semantics of XQuery 1.0 [XQuery 1.0: An XML Query Language] and XPath 2.0 [XML Path Language (XPath) 2.0].

Editors

Denise Draper, Michael Dyck, Peter Fankhauser, Mary Fernandez, Ashok Malhotra, Kristoffer Rose, Michael Rys, Jerome Simeon, Philip Wadler.

Family:

Xquery & XSLT

XQuery 1.1 fixes some bugs and adds some substantial new features to XQuery 1.0.

Editors

Scott Boag, Don Chamberlin, Mary Fernandez, Daniela Florescu, Jonathan Robie, Jerome Simeon.

Family:

Xquery & XSLT

XPath is a way to refer to parts of an XML document. XPath 2.0 is based on the XQuery 1.0 and XPath 2.0 Data Model (XDM), and also introduces Schema awareness and data typing.

Editors

Anders Berglund, Scott Boag, Don Chamberlin, Mary Fernandez, Michael Kay, Jonathan Robie, Jerome Simeon.

Family:

Xquery & XSLT

XQueryX Second Edition.

Editors

Jim Melton, Subramanian Muralidhar.

Family:

Xquery & XSLT

This document defines the W3C XQuery 1.0 and XPath 2.0 Data Model (XDM), which is the data model of [XPath 2.0], [XSLT 2.0], and [XQuery], and any other specifications that reference it. This data model is based on the [XPath 1.0] data model and earlier work on an [XML Query Data Model]. This document is the result of joint work by the [XSL Working Group] and the [XML Query Working Group].

Editors

Anders Berglund, Mary Fernandez, Ashok Malhotra, Jonathan Marsh, Marton Nagy, Norman Walsh.

Family:

Xquery & XSLT

This document defines constructor functions, operators and functions on the datatypes defined in [XML Schema Part 2: Datatypes Second Edition] and the datatypes defined in [XQuery 1.0 and XPath 2.0 Data Model]. It also discusses functions and operators on nodes and node sequences as defined in the [XQuery 1.0 and XPath 2.0 Data Model]. These functions and operators are defined for use in [XML Path Language (XPath) 2.0], [XQuery 1.0: An XML Query Language] and [XSL Transformations (XSLT) Version 2.0] and other related XML standards. The signatures and summaries of functions defined in this document are available at: http://www.w3.org/2005/xpath-functions.

Editors

Ashok Malhotra, Jim Melton, Norman Walsh, Michael Kay.

Family:

Xquery & XSLT

This document defines serialization of an instance of the data model as defined in [XQuery 1.0 and XPath 2.0 Data Model] into a sequence of octets. Serialization is designed to be a component that can be used by other specifications such as [XSL Transformations (XSLT) Version 2.0] or [XQuery 1.0: An XML Query Language].

Editors

Scott Boag, Michael Kay, Joanne Tong, Norman Walsh, Henry Zongaro.

Family:

Xquery & XSLT

This document specifies usage scenarios for XQuery.

Editors

Don Chamberlin, Peter Fankhauser, Daniela Florescu, Massimo Marchiori, Jonathan Robie.

Family:

Xquery & XSLT

This document specifies goals, requirements, and usage scenarios for the W3C XML Query (XQuery) data model and query language. It also includes, for each requirement, a corresponding status, indicating the status of the requirement in the XQuery 1.0 family of W3C Recommendations.

Editors

Don Chamberlin, Peter Fankhauser, Massimo Marchiori, Jonathan Robie.

Family:

Xquery & XSLT

XPath is a language for addressing parts of an XML document, designed to be used by both XSLT and XPointer.

Editors

James Clark, Steven DeRose.

Family:

Xquery & XSLT

This specification defines the syntax and semantics of XSLT, which is a language for transforming XML documents into other XML documents.

XSLT is designed for use as part of XSL, which is a stylesheet language for XML. In addition to XSLT, XSL includes an XML vocabulary for specifying formatting. XSL specifies the styling of an XML document by using XSLT to describe how the document is transformed into another XML document that uses the formatting vocabulary.

XSLT is also designed to be used independently of XSL. However, XSLT is not intended as a completely general-purpose XML transformation language. Rather it is designed primarily for the kinds of transformations that are needed when XSLT is used as part of XSL.

Editors

James Clark.

Family:

Xquery & XSLT

This document is a characterization of requirements and use cases for [XSL Transformations (XSLT) Version 2.1]. The Requirements list enhancements requested over time that may be addressed in XSLT 2.1.

Editors

Petr Cimprich.

Family:

Xquery & XSLT

This document provides a checklist of internationalization-related considerations when developing a specification. Most checklist items point to detailed supporting information in other documents. Where such information does not yet exist, it can be given a temporary home in this document. The dynamic page Internationalization Techniques: Developing specifications is automatically generated from this document.

Editors

Marcos Caceres, Addison Phillips.

Family:

Internationalization Best Practices for Spec Developers

This document is a registry of supplementary members for the Web App Manifest specification that provide additional metadata to an application manifest. This metadata can be used in a digital storefront or other surfaces where this web application may be marketed or ../distributed, or to enhance an installation dialog when installing a web application.

Editors

Aaron Gustafson.

Family:

Web App Manifest

This document contains a set of questions to be used when evaluating the security and privacy implications of web platform technologies.

Editors

Theresa O'Connor, Peter Snyder.

Family:

Self-Review Questionnaire: Security and Privacy

This CSS module describes how to collate style rules and assign values to all properties on all elements. By way of cascading and inheritance, values are propagated for all properties on all elements.

Editors

Elika Etemad, Tab Atkins Jr..

Family:

CSS Cascading and Inheritance

By way of cascading and inheritance, values are propagated for all properties on all elements. New in level 4 are the 'default' keyword and for the @import rule.

Editors

Elika Etemad, Tab Atkins Jr..

Family:

CSS Cascading and Inheritance

This document specifies an API that allows web applications to request and be notified of changes of the posture of a foldable device.

Editors

Diego Gonzalez-Zuniga, Kenneth Christiansen.

Family:

Device Posture

This document defines a set of ECMAScript APIs in WebIDL to allow media to be sent to and received from another browser or device implementing the appropriate set of real-time protocols. This specification is being developed in conjunction with a protocol specification developed by the IETF RTCWEB group and an API specification to get access to local media devices.

Editors

Cullen Jennings, Henrik Boström, Jan-Ivar Bruaroey.

Family:

WebRTC

This API defines a control surface for manipulating the network control bits (DSCP bits) of outgoing WebRTC packets, and the queueing priority of outgoing WebRTC packets under congestion.

Editors

Harald Alvestrand.

Family:

WebRTC

This document describes a set of use cases motivating the development of WebRTC Next Version (WebRTC-NV), as well as the requirements derived from those use cases.

Editors

Bernard Aboba.

Family:

WebRTC

This document defines a set of ECMAScript APIs in WebIDL to extend the WebRTC 1.0 API to enable user agents to support scalable video coding (SVC).

Editors

Bernard Aboba, Peter Thatcher.

Family:

WebRTC

This document defines a set of Javascript APIs that allow access to the statistical information about a PeerConnection.

Editors

Harald Alvestrand, Varun Singh, Henrik Boström.

Family:

WebRTC

This document defines a set of ECMAScript APIs in WebIDL to allow and application using WebRTC to assert an identity, and to mark media streams as only viewable by another identity. This specification is being developed in conjunction with a protocol specification developed by the IETF RTCWEB group.

Editors

Cullen Jennings, Martin Thomson.

Family:

WebRTC

This module of CSS defines keywords for the 'width' and 'height' properties to allow a designer to specify that an element should be as small as possible, as large as possible, or as large as possible up to the limit of its containing block. The 'width' and 'height' properties themselves are defined in the CSS Box Model.

Editors

Tab Atkins Jr., Elika Etemad.

Family:

CSS Box Sizing

This module extends the CSS sizing properties with keywords that represent content-based "intrinsic" sizes and context-based "extrinsic" sizes, allowing CSS to more easily describe boxes that fit their content or fit into a particular layout context. This is a delta spec over CSS Sizing Level 3.

Editors

Tab Atkins Jr., Elika Etemad.

Family:

CSS Box Sizing

Post-Spectre, we need to adopt some new strategies for safe and secure web development. This document outlines a threat model we can share, and a set of mitigation recommendations.

Editors

Mike West.

Family:

Post-Spectre

This section is informative.

CSS (Cascading Style Sheets) is a language for describing the rendering of HTML and XML documents on screen, on paper, in speech, etc. It uses various selectors, properties and values to style basic user interface elements in a document. This specification describes those user interface related selectors, properties and values that are proposed for CSS level 3 to style HTML and XML (including XHTML and XForms). It includes and extends user interface related features from the selectors, properties and values of CSS level 2 revision 1 and Selectors specifications.

Editors

Tantek Çelik, Florian Rivoal.

Family:

CSS Basic User Interface

CSS Basic UI Level 4 describes CSS properties and values to style basic user interface elements.

Editors

Florian Rivoal.

Family:

CSS Basic User Interface

This specification intends to provide APIs to allow websites to make an optimal decision when picking media content for the user. The APIs will expose information about the decoding and encoding capabilities for a given format but also output capabilities to find the best match based on the device’s display.

Editors

Mounir Lamouri, Chris Cunningham, Vi Nguyen.

Family:

Media Capabilities

This document defines a set of Fetch metadata request headers that aim to provide servers with enough information to make a priori decisions about whether or not to service a request based on the way it was made, and the context in which it will be used.

Editors

Mike West.

Family:

Fetch Metadata Request Headers

This document defines APIs for a database of records holding simple values and hierarchical objects. Each record consists of a key and some value. Moreover, the database maintains indexes over records it stores. An application developer directly uses an API to locate records either by their key or by using an index. A query language can be layered on this API. An indexed database can be implemented using a persistent B-tree data structure.

Editors

Ali Alabbas, Joshua Bell.

Family:

Indexed Database API

This document defines APIs for a database of records holding simple values and hierarchical objects.

Editors

Nikunj Mehta, Jonas Sicking, Eliot Graff, Andrei Popescu, Jeremy Orlow, Joshua Bell.

Family:

Indexed Database API

This document defines APIs for a database of records holding simple values and hierarchical objects. Each record consists of a key and some value. Moreover, the database maintains indexes over records it stores. An application developer directly uses an API to locate records either by their key or by using an index. A query language can be layered on this API. An indexed database can be implemented using a persistent B-tree data structure.

Editors

Ali Alabbas, Joshua Bell.

Family:

Indexed Database API

This module contains features to control panning and scrolling behavior with “snap positions”.

CSS is a language for describing the rendering of structured documents (such as HTML and XML) on screen, on paper, etc.

Editors

Matt Rakow, Jacob Rossi, Tab Atkins Jr., Elika Etemad.

Family:

CSS Scroll Snap

The set of CSS properties proposed in this document can be used in combination with the ruby elements of HTML to produce the stylistic effects needed to display ruby text appropriately relative to base text.

Editors

Elika Etemad, Koji Ishii, Xidorn Quan, Florian Rivoal.

Family:

CSS Ruby

This document defines the application/xml+ttml media type and provides a registry of identified TTML processor profiles.

Editors

Mike Dolan, Nigel Megitt, Glenn Adams.

Family:

TTML

This specification improves on ttml-imsc1.1 by supporting contemporary practices, while retaining compatibility with ttml-imsc1.1 documents. It provides one new feature, which permits external font files to be referenced explicitly. One existing feature has been clarified, and no features have been deprecated in this version.

Editors

Pierre-Anthony Lemieux.

Family:

TTML

This document specifies the ../distribution format exchange profile (DFXP) of the timed text authoring format (TT AF) in terms of a vocabulary and semantics thereof.

The timed text authoring format is a content type that represents timed text media for the purpose of interchange among authoring systems. Timed text is textual information that is intrinsically or extrinsically associated with timing information.

The Distribution Format Exchange Profile is intended to be used for the purpose of transcoding or exchanging timed text information among legacy distribution content formats presently in use for subtitling and captioning functions.

In addition to being used for interchange among legacy distribution content formats, DFXP content may be used directly as a distribution format, for example, providing a standard content format to reference from a <text> or <textstream> media object element in a [SMIL 2.1] document.

Editors

Glenn Adams, Pierre-Anthony Lemieux.

Family:

TTML

This document specifies the Second Edition of the Timed Text Markup Language (TTML), Version 2, also known as TTML2 (2e), in terms of a vocabulary and semantics thereof.

The Timed Text Markup Language is a content type that represents timed text media for the purpose of interchange among authoring systems. Timed text is textual information that is intrinsically or extrinsically associated with timing information.

It is intended to be used for the purpose of transcoding or exchanging timed text information among legacy ../distribution content formats presently in use for subtitling and captioning functions.

In addition to being used for interchange among legacy ../distribution content formats, TTML Content may be used directly as a distribution format, for example, providing a standard content format to reference from a <track> element in an [HTML] document, or a <text> or <textstream> media element in a [SMIL 3.0] document.

Editors

Glenn Adams, Cyril Concolato.

Family:

TTML

This specification defines two profiles of TTML2: a text-only profile and an image-only profile. These profiles are intended to be used across subtitle and caption delivery applications worldwide, thereby simplifying interoperability, consistent rendering and conversion to other subtitling and captioning formats.

Editors

Pierre-Anthony Lemieux.

Family:

TTML

This document captures technical requirements for [ttml-imsc1.1], the next revision of [ttml-imsc1.0.1].

Editors

Pierre-Anthony Lemieux.

Family:

TTML

This document specifies two profiles of TTML1: a text-only profile and an image-only profile. These profiles are intended to be used across subtitle and caption delivery applications worldwide, thereby simplifying interoperability, consistent rendering and conversion to other subtitling and captioning formats.

Editors

Pierre-Anthony Lemieux.

Family:

TTML

The Simple Online Delivery profile is focused on streamlined delivery of closed captions on the Internet, supporting core TTML features to deliver content originating legacy formats such as CEA-608 and -708 content, and is targeted primarily for delivery in US markets.

Editors

Glenn Adams, Monica Martin, Sean Hayes.

Family:

TTML

This document specifies usage scenarios and requirements for a timed text authoring format. A timed text authoring format is a content type that represents timed text media for the purpose of interchange among authoring systems. Timed text is textual information that is intrinsically or extrinsically associated with timing information.

Editors

Glenn Adams.

Family:

TTML

This document specifies the Second Edition of the Timed Text Markup Language (TTML), Version 2, also known as TTML2 (2e), in terms of a vocabulary and semantics thereof.

The Timed Text Markup Language is a content type that represents timed text media for the purpose of interchange among authoring systems. Timed text is textual information that is intrinsically or extrinsically associated with timing information.

It is intended to be used for the purpose of transcoding or exchanging timed text information among legacy ../distribution content formats presently in use for subtitling and captioning functions.

In addition to being used for interchange among legacy ../distribution content formats, TTML Content may be used directly as a distribution format, for example, providing a standard content format to reference from a <track> element in an [HTML] document, or a <text> or <textstream> media element in a [SMIL 3.0] document.

Editors

Glenn Adams, Cyril Concolato.

Family:

TTML

This document defines a set of JavaScript APIs that let a Web application manage how audio is rendered on the user audio output devices.

Editors

Justin Uberti, Guido Urdaneta, youenn fablet.

Family:

Audio Output Devices API

This module describes multi-column layout in CSS. It builds on the CSS3 Box model module and adds functionality to flow the content of an element into multiple columns.

Editors

Håkon Wium Lie, Florian Rivoal, Rachel Andrew.

Family:

CSS Multi-column Layout

This specification describes an API that can be used to understand the visibility and position of DOM elements ("targets") relative to a containing element or to the top-level viewport ("root"). The position is delivered asynchronously and is useful for understanding the visibility of elements and implementing pre-loading and deferred loading of DOM content.

Editors

Stefan Zager, Emilio Cobos Álvarez, Michael Blain.

Family:

Intersection Observer

This document describes apis for clipboard operations such as copy/cut and paste, or drag and drop in web applications.

Editors

Gary Kacmarcik, Grisha Lyukshin.

Family:

Clipboard API and events

HTML is the World Wide Web's core markup language. Originally, HTML was primarily designed as a language for semantically describing scientific documents. Its general design, however, has enabled it to be adapted, over the subsequent years, to describe a number of other types of documents and even applications.

Family:

HTML

This specification defines HTML form enhancements that provide access to the audio, image and video capture capabilities of the device.

Editors

Anssi Kostiainen, Ilkka Oksanen, Dominique Hazaël-Massieux.

Family:

HTML

This document contains proposals for new features to be added to HTML to support bidirectional text in languages such as Arabic, Hebrew, Persian, Thaana, Urdu, etc.

Editors

Aharon Lanin, Richard Ishida.

Family:

HTML

This specification defines a longdesc attribute to link extended descriptions with images in HTML5-based content.

Editors

Charles McCathieNevile, Mark Sadecki.

Family:

HTML

HTML microdata [MICRODATA] is an extension to HTML used to embed machine-readable data into HTML documents. Whereas the microdata specification describes a means of markup, the output format is JSON. This specification describes processing rules that may be used to extract RDF [RDF-CONCEPTS] from an HTML document containing microdata.

Editors

Gregg Kellogg.

Family:

HTML

HTML 5 defines the fifth major revision of the core language of the World Wide Web, HTML. "HTML 5 differences from HTML 4" describes the differences between HTML 4 and HTML 5 and provides some of the rationale for the changes. This document may not provide accurate information as the HTML 5 specification is still actively in development. When in doubt, always check the HTML 5 specification itself. [HTML5]

Editors

Simon Pieters.

Family:

HTML

Describes a method for declaring inert DOM subtrees in HTML and manipulating them to instantiate document fragments with identical contents

Editors

Dimitri Glazkov, Rafael Weinstein, Tony Ross.

Family:

HTML

The ruby markup model currently described in the HTML specification is limited in its support for a number of features, notably jukugo and double-sided ruby, as well as inline ruby. This specification addresses these issues by introducing new elements and changing the ruby processing model. Specific care has been taken to ensure that authoring remains as simple as possible.

Editors

Robin Berjon.

Family:

HTML

This document captures the use cases and requirements for standardizing a solution for responsive images.

Editors

Marcos Caceres, Mathew Marquis, Yoav Weiss, David Newton.

Family:

HTML

This document looks at a number of use cases involving ruby, and examines the pros and cons of a number of alternative approaches for meeting those use cases using the current HTML5 model, the XHTML Ruby Annotation model, and two other models. The aim is to clarify which use cases are supported by the existing markup models (HTML5 or XHTML), and where they are not, provide suggestions about how the markup model could be adapted to support those use cases. Implementers and standards developers can then take this background information and the suggestions in this document to specify and implement a comprehensive markup model for ruby in HTML5.

Editors

Richard Ishida.

Family:

HTML

This document describes the HTML markup language and provides details to help producers of HTML content create documents that conform to the language. It is not the normative specification but intended for authors.

Editors

Michael[tm] Smith.

Family:

HTML

This document is a strict subset of the HTML5 specification that omits user-agent (UA) implementation details. It is targeted toward Web authors and others who are not UA implementors and who want a view of the HTML specification that focuses more precisely on details relevant to using the HTML language to create Web documents and Web applications.

Editors

Robin Berjon, Travis Leithead, Silvia Pfeiffer, Erika Doyle Navara, Theresa O'Connor.

Family:

HTML

This specification is an extension to the HTML5 specification. It defines an element to be used for the identification of the main content area of a document. The main element formalises the common practice of identification of the main content section of a document using the id values such as 'content' and 'main'. It also defines an HTML element that embodies the semantics and function of the WAI-ARIA landmark role=main.

Editors

Steve Faulkner.

Family:

HTML

This guide aims to help publishers and consumers of HTML data use it well. With several syntaxes and vocabularies to choose from, it provides guidance about how to decide which meets the publisher's or consumer's needs. It discusses when it is necessary to mix syntaxes and vocabularies and how to publish and consume data that uses multiple formats. It describes how to create vocabularies that can be used in multiple syntaxes and general best practices about the publication and consumption of HTML data.

Editors

Jeni Tennison.

Family:

HTML

Editors

Norman Walsh.

Family:

HTML

XHTML Media Types recapitulates which media types can and should be used with the different flavors of XHTML, and under what conditions.

Editors

Shane McCarron.

Family:

HTML

Offline Web Applications highlights the features in HTML 5 that address the challenge of building Web applications that work while offline.

Editors

Anne van Kesteren, Ian Hickson.

Family:

HTML

This paper introduces the concept of a "Rich Web Application Backplane" -- a set of common building blocks for web applications. We argue that submission, data models, model-view binding and behavior, and web components can provide a common infrastructure for multiple markup formats. Further, we propose a common infrastructure for both declarative and imperative web programming languages. By aligning APIs and their declarative representations, we hope to support both implementation approaches and increase interoperability between them.

Editors

Mark Birbeck, John Boyer, Alfred S. Gilman, Kevin Kelly, Steven Pemberton, Charles Wiecha.

Family:

HTML

The XML Events module defined in this specification provides XML languages with the ability to uniformly integrate event listeners and associated event handlers with Document Object Model (DOM) Level 2 event interfaces [DOM2EVENTS]. The result is to provide an interoperable way of associating behaviors with document-level markup.

Editors

Shane McCarron, Steven Pemberton, T.V. Raman.

Family:

HTML

This document describes XML Schemas for XHTML 1.0.

Editors

Masayasu Ishikawa.

Family:

HTML

The XHTML+SMIL profile defines a set of XHTML abstract modules that support a subset of the SMIL 2.0 specification.

Editors

Aaron Patterson, Patrick Schmitz.

Family:

HTML

From the early days of the World Wide Web, Web Agents had been extended to support more types of contents. The recent developments of XML and the possibility to mix mupltiple XML Namespaces in the document reiterated the need to extend implementations and relaying on add-on softwares to accomplish tasks not supported by default in the implementation. In other words, we have several XML languages to represent different parts of Web pages (XHTML, SVG, MathML, XForms, etc.), we now need a well defined mechanism that allow different specialized tools to work together and handled these compound documents.

This W3C Note contains a non-exhaustive list of requirements to work on a Component Extension API. The goal of this API is to extend the ability of a Web application. Note that the Web application can be either on the server side or on a client side, and does not automatically implies interaction with a user or having a Web browser.

Editors

Angel Diaz, Jon Ferraiolo, Philippe Le Hégaret, Chris Lilley, Charles McCathieNevile, Tapas Roy, Ray Whitmer.

Family:

HTML

"Ruby" are short runs of text alongside the base text, typically used in East Asian documents to indicate pronunciation or to provide a short annotation. This document proposes a set of CSS properties associated with the 'Ruby' elements. They can be used in combination with the Ruby elements of HTML.

Editors

Marcin Sawicki, Michel Suignard, Masayasu Ishikawa, Martin Dürst, Tex Texin.

Family:

HTML

Editors

Tomihisa Kamada, Masayasu Ishikawa, Shinichi Matsui.

Family:

HTML

Editors

Dan Connolly, Lauren Wood.

Family:

HTML

Family:

HTML

Editors

Stu Weibel.

Family:

HTML

This document defines a way to include and reuse HTML documents in other HTML documents.

Editors

Dimitri Glazkov, Hajime Morita.

Family:

HTML

HTML 5 defines the fifth major revision of the core language of the World Wide Web, HTML. This document describes the set of guiding principles used by the HTML Working Group for the development of HTML5. The principles offer guidance for the design of HTML in the areas of compatibility, utility and interoperability.

Editors

Anne van Kesteren, Maciej Stachowiak.

Family:

HTML

This practical guide provides you with the knowledge required to effectively use the XML Binding Language 2.0. It introduces both the basic and advanced concepts of XBL and describes its syntax and scenarios that should be considered best-practice. It also describes the purpose of the language elements described in the XBL 2.0 specification.

XBL describes the ability to associate elements in one document with script, event handlers, styles, and more complex content models in another document. You can use XBL to re-order and wrap content so that, for instance, simple HTML or XHTML markup can have complex CSS styles applied without requiring that the markup be polluted with multiple div elements. In addition, if you are a programmer, you can use XBL to implement new DOM interfaces, and, in conjunction with other specifications, it enables arbitrary XML tag sets to be treated as "widgets" (pluggable user interface components).

Editors

Lachlan Hunt, Marcos Caceres.

Family:

HTML

This specification defines APIs to select objects within a document.

Editors

Ryosuke Niwa.

Family:

Selection API

Web Content Accessibility Guidelines (WCAG) 2.1 covers a wide range of recommendations for making Web content more accessible. Following these guidelines will make content accessible to a wider range of people with disabilities, including blindness and low vision, deafness and hearing loss, learning disabilities, cognitive limitations, limited movement, speech disabilities, photosensitivity, and combinations of these. These guidelines address accessibility of web content on desktops, laptops, tablets, and mobile devices. Following these guidelines will also often make your Web content more usable to users in general.

Editors

Andrew Kirkpatrick, Joshue O Connor, Alastair Campbell, Michael Cooper.

Family:

WCAG

Provides detailed information about the intent of each WCAG 2.0 success criterion and describes benefits, examples, failure conditions, and recommended techniques in various technologies.

Editors

Michael Cooper, Andrew Kirkpatrick, Joshue O Connor.

Family:

WCAG

Documents authoring practices in various technologies that may be used to satisfy the WCAG 2.0 success criteria.

Editors

Michael Cooper, Andrew Kirkpatrick, Joshue O Connor.

Family:

WCAG

WCAG-EM provides an approach for evaluating how websites - including web applications and websites for mobile devices - conform to WCAG 2.0. It covers different situations, including self-assessment and third-party evaluation.

Editors

Eric Velleman, Shadi Abou-Zahra.

Family:

WCAG

Describes how the Web Content Accessibility Guidelines (WCAG) 2.0 and its principles, guidelines, success criteria and conformance model can be applied to non-Web Information and Communications Technologies (ICT), including non-web documents and software.

Editors

Michael Cooper, Peter Korn, Andi Snow-Weaver, Gregg Vanderheiden.

Family:

WCAG

Web Content Accessibility Guidelines (WCAG) 2.0 covers a wide range of recommendations for making Web content more accessible. Following these guidelines will make content accessible to a wider range of people with disabilities, including blindness and low vision, deafness and hearing loss, learning disabilities, cognitive limitations, limited movement, speech disabilities, photosensitivity and combinations of these. Following these guidelines will also often make your Web content more usable to users in general.

WCAG 2.0 success criteria are written as testable statements that are not technology-specific. Guidance about satisfying the success criteria in specific technologies, as well as general information about interpreting the success criteria, is provided in separate documents. See Web Content Accessibility Guidelines (WCAG) Overview for an introduction and links to WCAG technical and educational material.

WCAG 2.0 succeeds Web Content Accessibility Guidelines 1.0 [WCAG10], which was published as a W3C Recommendation May 1999. Although it is possible to conform either to WCAG 1.0 or to WCAG 2.0 (or both), the W3C recommends that new and updated content use WCAG 2.0. The W3C also recommends that Web accessibility policies reference WCAG 2.0.

Editors

Ben Caldwell, Michael Cooper, Loretta Guarino Reid, Gregg Vanderheiden.

Family:

WCAG

Requirements used for development of WCAG 2.0.

Editors

Gregg Vanderheiden, John Slatin, Wendy Chisholm.

Family:

WCAG

This document describes techniques for authoring accessible Hypertext Markup Language (HTML) content (refer to HTML 4.01 [HTML4]). This document is intended to help authors of Web content who wish to claim conformance to "Web Content Accessibility Guidelines 1.0" ([WCAG10]). While the techniques in this document should help people author HTML that conforms to "Web Content Accessibility Guidelines 1.0", these techniques are neither guarantees of conformance nor the only way an author might produce conforming content.

This document is part of a series of documents about techniques for authoring accessible Web content. For information about the other documents in the series, please refer to "Techniques for Web Content Accessibility Guidelines 1.0" [WCAG10-TECHS].

Note: This document contains a number of examples that illustrate accessible solutions in CSS but also deprecated examples that illustrate what content developers should not do. The deprecated examples are highlighted and readers should approach them with caution -- they are meant for illustrative purposes only.

Editors

Wendy Chisholm, Gregg Vanderheiden, Ian Jacobs.

Family:

WCAG

Gateway to a series of related documents that provide techniques for satisfying the requirements defined in WCAG 1.0.

Editors

Wendy Chisholm, Gregg Vanderheiden, Ian Jacobs.

Family:

WCAG

Techniques that apply across technologies for authors of Web content who wish to claim conformance to WCAG 1.0

Editors

Wendy Chisholm, Gregg Vanderheiden, Ian Jacobs.

Family:

WCAG

This document describes techniques for authoring accessible Cascading Style Sheets (CSS). Cascading Style Sheets are defined by the W3C Recommendations "CSS Level 1" [CSS1] and "CSS Level 2" [CSS2]. This document is intended to help authors of Web content who wish to claim conformance to "Web Content Accessibility Guidelines 1.0" ([WCAG10]). While the techniques in this document should help people author CSS that conforms to "Web Content Accessibility Guidelines 1.0", these techniques are neither guarantees of conformance nor the only way an author might produce conforming content.

This document is part of a series of documents about techniques for authoring accessible Web content. For information about the other documents in the series, please refer to "Techniques for Web Content Accessibility Guidelines 1.0" [WCAG10-TECHS].

Note: This document contains a number of examples that illustrate accessible solutions in CSS but also deprecated examples that illustrate what content developers should not do. The deprecated examples are highlighted and readers should approach them with caution -- they are meant for illustrative purposes only.

Editors

Wendy Chisholm, Gregg Vanderheiden, Ian Jacobs.

Family:

WCAG

These guidelines explain how to make Web content accessible to people with disabilities. The guidelines are intended for all Web content developers (page authors and site designers) and for developers of authoring tools. The primary goal of these guidelines is to promote accessibility. However, following them will also make Web content more available to all users, whatever user agent they are using (e.g., desktop browser, voice browser, mobile phone, automobile-based personal computer, etc.) or constraints they may be operating under (e.g., noisy surroundings, under- or over-illuminated rooms, in a hands-free environment, etc.). Following these guidelines will also help people find information on the Web more quickly. These guidelines do not discourage content developers from using images, video, etc., but rather explain how to make multimedia content more accessible to a wide audience.

This is a reference document for accessibility principles and design ideas. Some of the strategies discussed in this document address certain Web internationalization and mobile access concerns. However, this document focuses on accessibility and does not fully address the related concerns of other W3C Activities. Please consult the W3C Mobile Access Activity home page and the W3C Internationalization Activity home page for more information.

This document is meant to be stable and therefore does not provide specific information about browser support for different technologies as that information changes rapidly. Instead, the Web Accessibility Initiative (WAI) Web site provides such information (refer to [WAI-UA-SUPPORT]).

This document includes an appendix that organizes all of the checkpoints by topic and priority. The checkpoints in the appendix link to their definitions in the current document. The topics identified in the appendix include images, multimedia, tables, frames, forms, and scripts. The appendix is available as either a tabular summary of checkpoints or as a simple list of checkpoints.

A separate document, entitled "Techniques for Web Content Accessibility Guidelines 1.0" ([TECHNIQUES]), explains how to implement the checkpoints defined in the current document. The Techniques Document discusses each checkpoint in more detail and provides examples using the Hypertext Markup Language (HTML), Cascading Style Sheets (CSS), Synchronized Multimedia Integration Language (SMIL), and the Mathematical Markup Language (MathML). The Techniques Document also includes techniques for document validation and testing, and an index of HTML elements and attributes (and which techniques use them). The Techniques Document has been designed to track changes in technology and is expected to be updated more frequently than the current document. Note. Not all browsers or multimedia tools may support the features described in the guidelines. In particular, new features of HTML 4.0 or CSS 1 or CSS 2 may not be supported.

"Web Content Accessibility Guidelines 1.0" is part of a series of accessibility guidelines published by the Web Accessibility Initiative. The series also includes User Agent Accessibility Guidelines ([WAI-USERAGENT]) and Authoring Tool Accessibility Guidelines ([WAI-AUTOOLS]).

Editors

Wendy Chisholm, Gregg Vanderheiden, Ian Jacobs.

Family:

WCAG

The W3C Accessibility Guidelines (WCAG) 3.0 provide a wide range of recommendations for making web content more accessible to users with disabilities. Following these guidelines will address many of the needs of users with blindness, low vision and other vision impairments; deafness and hearing loss; limited movement and dexterity; speech disabilities; sensory disorders; cognitive and learning disabilities; and combinations of these. These guidelines address accessibility of web content on desktops, laptops, tablets, mobile devices, wearable devices, and other web of things devices. They address various types of web content including static content, interactive content, visual and auditory media, and virtual and augmented reality. The guidelines also address related web tools such as user agents (browsers and assistive technologies), content management systems, authoring tools, and testing tools.

Editors

Jeanne F Spellman, Rachael Bradley Montgomery, Shawn Lauriat, Michael Cooper.

Family:

WCAG

The Requirements for WCAG 3.0 document is the next phase in the development of the next major upgrade to accessibility guidelines that will be the successor to Web Content Accessibility Guidelines (WCAG) 2 series. The Silver Task Force of the Accessibility Guidelines Working Group and the W3C Silver Community group have partnered to incubate the needs, requirements, and structure for the new accessibility guidance.

Editors

Jeanne F Spellman, Shawn Lauriat, Michael Cooper.

Family:

WCAG

Web Content Accessibility Guidelines (WCAG) 2.2 covers a wide range of recommendations for making Web content more accessible. Following these guidelines will make content more accessible to a wider range of people with disabilities, including accommodations for blindness and low vision, deafness and hearing loss, limited movement, speech disabilities, photosensitivity, and combinations of these, and some accommodation for learning disabilities and cognitive limitations; but will not address every user need for people with these disabilities. These guidelines address accessibility of web content on desktops, laptops, tablets, and mobile devices. Following these guidelines will also often make Web content more usable to users in general.

Editors

Charles Adams, Alastair Campbell, Rachael Bradley Montgomery, Michael Cooper, Andrew Kirkpatrick.

Family:

WCAG

Explores how testability and page-based conformance verification of accessibility guidelines presents challenges for a broad range of websites and web applications.

Editors

Michael Cooper, Peter Korn, Charles Hall.

Family:

WCAG

This document is a gap analysis and roadmap for the state of accessibility for people with learning and cognitive disabilities when using the Web and information technologies.

Editors

Lisa Seeman-Horwitz, Michael Cooper.

Family:

WCAG

Outlines the requirements that the Web Content Accessibility Guidelines Working Group has set for the development of Web Content Accessibility Guidelines (WCAG) 2.0 extensions. These extension requirements build on the existing requirements for WCAG 2.0, and are designed to work in harmony with the WCAG 2.0 standard.

Editors

Michael Cooper, Andrew Kirkpatrick, Joshue O Connor.

Family:

WCAG

Mobile Accessibility: How WCAG 2.0 and Other W3C/WAI Guidelines Apply to Mobile” describes how the Web Content Accessibility Guidelines (WCAG) 2.0 and its principles, guidelines, and success criteria can be applied to mobile web content, mobile web apps, native apps, and hybrid apps using web components inside native apps. It provides informative guidance, but does not set requirements. It also highlights the relevance of the User Agent Accessibility Guidelines 2.0 in the mobile context.

Editors

Kimberly Patch, Jeanne F Spellman, Kathleen Wahlbin.

Family:

WCAG

This document provides a review and analysis of guidelines and articles relating to the needs of older people with Web accessibility needs due to ageing, and compares these with the needs of people with disabilities as already addressed in WAI guidelines. The focus is particularly on Europe but applies internationally as well. This review is being undertaken in order to inform the development of educational materials which can better promote the needs of people who have accessibility needs due to ageing, and potential development of profiles and/or extensions on WAI guidelines.

Editors

Andrew Arch.

Family:

WCAG

This specification defines an API for sharing text, links and other content to an arbitrary destination of the user's choice.

Editors

Matt Giuca, Eric Willigers.

Family:

Web Share API

This note highlights some of the unique characteristics of spatial data within the broader realm of ethical use of data. A brief analysis of the relationship between law and ethics explains that responsible use is not mandatory. Nevertheless, both legal and ethical frameworks play an important role in shaping what can be considered “responsible”. As do the perspectives of those who interact closely with spatial data: the developers, the users and the regulators. Therefore this note not only provides an insight into the relevant legislation and ethics guidelines, but also considers the principles of ethical data sharing from each of these three perspectives. The principles are made practical by providing concrete communication guidelines and showing examples of good practice.

Editors

JOSEPH ABHAYARATNA, Ed Parsons.

Family:

Spatial Data

This CSS module defines pseudo-elements, abstract elements that represent portions of the CSS render tree that can be selected and styled.

Editors

Daniel Glazman, Elika Etemad, Alan Stearns.

Family:

CSS Pseudo-Elements

This draft contains the features of CSS relating to borders and backgrounds. The main extensions compared to level 2 are borders consisting of images, boxes with multiple backgrounds, boxes with rounded corners and boxes with shadows.

Editors

Bert Bos, Elika Etemad, Brad Kemper.

Family:

CSS Backgrounds and Borders

This specification describes the margin and padding properties, which create spacing in and around a CSS box.

Editors

Elika Etemad.

Family:

CSS Box Model

This specification describes the margin and padding properties, which create spacing in and around a CSS box. It may later be extended to include borders (currently described in [css-backgrounds-3]).

Editors

Elika Etemad.

Family:

CSS Box Model

This document collects together into one definition all the specs that together form the current state of Cascading Style Sheets (CSS) as of 2020. The primary audience is CSS implementers, not CSS authors, as this definition includes modules by specification stability, not Web browser adoption rate.

Editors

Tab Atkins Jr., Elika Etemad, Florian Rivoal.

Family:

CSS

This CSS module describes the contain property, which indicates that the element’s subtree is independent of the rest of the page. This enables heavy optimizations by user agents when used well.

Editors

Tab Atkins Jr., Florian Rivoal.

Family:

CSS Containment